@Medievil As far as i know dunfell is the most stable branch.i used yocto from dunfell and meta-qt5 from dunfell.I did not make any modification to package configurations.Everything is working fine

@SpyerGame Did you check the board list in the documentation page I linked to ?

You should also take into account the compute requirements that might require an NVIDIA GPU for example.

@Raghav said in Image not loading:

import QtQuick.Layouts 1.15
import QtQuick.Controls 2.15

import QtQuick.Layouts 1.15 <=version number is dropped in Qt6 import QtQuick.Controls 2.15 <=version number is dropped in Qt6 simply import QtQuick.Layouts import QtQuick.Controls

Thanks for the reply , yeah I was thinking same to contact sales team.

Thank you .

@SGaist Thank you for your reponse. I will check both QtTestModule and Squish.

@SGaist I don't think so but in the meantime I don't see any package which could do it. My board support OpenGl ES2 so I tried some stuff like adding "PACKAGE CONFIG += "gles2" " to my qtbase bb file but nothing has changed ...

Also tried to add PACKAGECONFIG_append_pn-qtbase = "gles2" in my local.conf but no change.

After some googling, I found that the error was printed by this code : https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbbackingstore.cpp?h=dev (line 371)

Edit: Closing this issue, it was a problem of platform (by default it was using x11 which is not the one used by my embedded device) . Thanks a lot for your help again !

Do you really need two different objects to communicate with these devices ?

Hi

One reason can be the touch setup
-- Can you please explain a little more on this?
Well since it only happens sometimes, i guess its not that.
I have seen something like it when touch was setup for gestures and you kinda moved the finger
when you "clicked" it would then start the gesture and sort of eat the click.

Could also be a bug in Qt4.8 that the later fixed with Grabmouse
-- Is there any defect ID that you remember? That will add more waitage for the understanding.
Sorry nope. it was a duck. It was due to calling a message box that would run event loop and
button would not redraw before after.

One of the other thought that I have is, if this is really a UI issue or this is being a side effect due to any other -problems such as CPU load, Memory full, etc. Do you think it is possible?

Yes that is really possible if the target is low powered board and it's low on say ram then the same task might
suddenly take much longer and the button will appear down.

Have you tested with a button that does nothing and see if that can get stuck?

@prinzkm I don't have any experience with Qt on embedded devices. However, on the same page you provided the screenshot it has a section on "Available Keyboard Drivers". These are Qt-specific drivers, as far as I understand. It seems that currently only two drivers are available: TTY and LinuxInput. By default Qt is only compiled with support for TTY. Unfortunately, this is also the driver which intercepts Ctrl+Alt+F1 and Ctrl+Alt+Backspace. Therefore, you should have a look at the other driver. My understanding is that for this to work you need to compile Qt yourself with the LinuxInput driver enabled (by providing the command line option -qt-kbd-linuxinput when configuring Qt before compilation. I hope, somebody else can help you with these keyboard drivers.

@kumararajas said in QWebView - On Click CPU Performance:

Thank you @Konstantin-Tokarev This explanation means a lot. This helps us to understand that we are using older version of Qt WebKit and which is not really efficient.
At this moment of time, we don't have a plan to update to the latest version. We will have to find a work around in the application to manage the situation.

Does it mean that you cannot change any bits of software in your system and you are limited to workarounds on the side of web page? If so, it's really sad situation.

If you are able to change software, you are strongly adviced to use QtWebKit 2.3.4, or at least give it a try.

@kumararajas said in QWebView - On Click CPU Performance:

@Konstantin-Tokarev Yes, we have been trying to understand who consumes the lot of CPU and why. When I did profiling using gprof/perf tools, I can find out that which function in my application consumes a lot, but that does not root in to the framework, which is webkit. Do you recommend any method which I can profile the framework side as well?

Don't use gprof. This tool claims to measure time spent in functions, but in fact measures totally different thing. And, as you've already discovered, it can only profile code which was rebuilt with -pg flag.

As for perf, it is decent tool. On older systems oprofile can be used. Make sure that your QtWebKit library is not stripped

And even if we find issues in the framework, at this moment we are not in a position to upgrade the system. So we will identify the work around and live with it ( Already found couple of work around solution, which I will be sharing it in a while here )

I have no idea what do you mean here, and I don't really want to be in your shoes. (/me once had to reverse engineer and then binary patch 3rd party kernel driver with no source code, but at least there were no problems with updating target system)

Reason for asking such question is,
Someone might have faced similar problem and might have the ready solution. Instead of I spending lot of time in exploring, researching, debugging, etc, I could post it here to know if someone knows about it. However, in parallel to posting this question, I have been doing things in parallel if in case I don't get the answer. For this post, you being a legend on webkit, you have mentioned that it could be a problem of webkit version that we use, which makes sense and unveils the root cause.

I'm far from being legend, and there may be other reasons of high CPU consumptions, maybe several factors at once. It can be that WebKit just doesn't have enough memory to process page, and system is thrashing (you'll see high sys usage in top then).

When I touch the report, does Qt Web Kit renders the whole web page again?

If you are not using QWebSettings::TiledBackingStoreEnabled and are not using accelerated composting on QGLWidget viewport, and are not using QWebPage::setPreferredContentsSize, then QtWebKit definitely reners whole page again after scroll. It doesn't redraw old pixel, but it performs whole rendering procedure with QPainter being clipped to update region. It may easily be a bottleneck if page is complex

Hi @Geeva,

@Geeva said in JSON with multi tasking:

@JKSH Thanks for solving basic confusion. I have one more doubt also. Here, I have attached program for verification. I hope you can provide a proper solution

You're welcome. I'm happy to teach you basics. However, verifying your program is too difficult to do on a forum.

You need to do 2 things:

Take C++ lessons Practice writing and debugging simple programs for your hardware

Hi,

there are 2 possible cases:

If you are sure that void DistanceThread::run() exit after first iteration then you are setting "flagforbreak" or "diststop" in between. So could you please check the slots of those signals which you are emitting? (May be the flag set from there).

DistanceThread::run() is still executing but your conditions (i saw complex nested "If"s there :) ) may not meet anytime.(Hope U will debug it ensure that.

Regards,
Rajeesh Raveendran

@develop-it See my answer here: http://forum.qt.io/topic/68325/the-library-could-not-be-configured-for-supporting-multi-threaded-applications
If you have another error while executing make then you should post it here, else it is not possible to help you.

It is working fine. Thanks for the help

@DEEPAK-NATH I'm not the one with the problem...